Skip to content

feat(preview): expose retained recording operation evidence - #824

Merged
Mjones13 merged 4 commits into
mainfrom
work/efficiency-closeout-5af0f65c-20261102
Nov 3, 2026
Merged

Mjones13 merged 4 commits into
mainfrom
work/efficiency-closeout-5af0f65c-20261102

Conversation

@Mjones13

@Mjones13 Mjones13 commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Timed-out Browser recording requests can settle after the caller has lost its response, leaving agents unable to inspect retained broker evidence safely. Add the read-only preview_recording_operation MCP tool, scoped to the caller and an explicit tab, with optional exact request/client/connection selection.

The lookup reports pending, unknown, settled, ambiguous or unavailable evidence without contacting a host, retrying a recording or changing a fence. Accepted late replies retain a bounded, reduced projection; settlement does not claim physical recorder completion or artifact transfer. Both preview toolkits expose the additive read, preserving older wire operations.

Validation: 26 focused tests and 78 existing broker/MCP guards passed on the VPS; the new public registration assertion fails against unchanged source. Scoped lint and formatting, strict boundary checking and independent correctness review passed. Local typechecking was unavailable because the official private-cache guard rejected the reused dependency layout. Scoped Knip exited zero but reported unavailable mobile config; Required CI Check passed on final head 44d39b2 (run41559427182), including typecheck, build, lint, both web shards and all eight server shards. The CI repairs preserve production behavior and test assertions; the Mermaid fixture now explicitly awaits its dynamic imports.

Refs #579. Historical recording outcomes and original Workstreams native acceptance remain separate. No installed runtime was changed.

Implemented with Codex GPT-6.1 Sol; reviewed with Sol Max under Codex-only Frontier Max in Jones Code.


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

@Mjones13

Mjones13 commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor Author

The Typecheck repair is now at head 76f5a2fb55f79379611c7aa4e0d94c290a57e7bf. The remaining reported server-shard failure is an unchanged UsageService regression: its August 1 fixture has aged past the 92-day retention cutoff. The same focused assertion fails outside the recording feature.

Separate PR #827 pins that test's Effect clock inside the intended window, preserving all assertions and production behavior. Its focused before/after regression is established; full current-head CI remains required. Once #827 lands normally, this branch will merge main and rerun qualification. No failing check is waived or treated as passing.

@Mjones13

Mjones13 commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor Author

The 7e475ea run passed all eight server shards, typecheck, build and lint. Web shard 1 failed only the unchanged Mermaid MathML sanitizer test: its one-second mount poll expired before any mount. The math-only KaTeX import is an additional unawaited dependency on that path, so import timing is the source-supported explanation rather than a directly measured import span. The same unchanged seven-test module passed on the VPS (MathML case 333 ms), consistent with cold-import timing dependence.

44d39b2 adds one explicit await act(() => vi.dynamicImportSettled()) in the sanitizer case, using the existing AttachmentImage test pattern. Production code, all fourteen recording-change files, sanitizer assertions, test IDs, retries and time limits are unchanged. Focused VPS verification: 7/7 passed, no skips; formatting passed; lint has zero warnings/errors. Fresh current-head CI remains required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant